-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.x] Add Forge facade for Laravel integration #177
Conversation
This is great, thanks @stevebauman. Let's get the Facade documentor added, then we can look to merge this. Setting to draft for now. |
Ok sounds good @jbrooksuk! I've added the new GitHub action, though it may need approval to be ran (it doesn't look like it's being executed in this PR), so I've ran it manually on my end for now. Static analysis will also fail right now, not sure if how we should handle that. Let me know if you have any other feedback or things you'd like adjusted, thanks for your time! |
@stevebauman the workflow will only be executed on a push to master or an Btw, you may want to add the |
Ah awesome thanks @driesvints! Looks like we're all green now! 🎉 |
A Great Thanks for add Forge. |
This PR adds a
Forge
facade for Laravel integration, allowing users to call Forge API methods using a singleton with an API token defined in theirservices.php
configuration file:I did not add
illuminate/support
to thecomposer.json
, as I'm sure we don't want to make it a requirement for users of the SDK, but anyone installing this into a Laravel application will be able to utilize the facade as soon as they add an API key to their env/config.This also has the added benefit of easy testing due to the Facade integration:
If this is something you'd still like to avoid having in the SDK, no worries at all! Really appreciate your time ❤️